Skip to content

Bump ClickHouse.Driver to 1.5.0 - #69

Merged
alex-clickhouse merged 1 commit into
mainfrom
alex-clickhouse/bump-driver-1.5.0
Oct 14, 2026
Merged

alex-clickhouse merged 1 commit into
mainfrom
alex-clickhouse/bump-driver-1.5.0

Conversation

@alex-clickhouse

Copy link
Copy Markdown
Collaborator

Moves the ClickHouse.Driver pin from 1.4.0 to 1.5.0 in the provider and in both test projects. The three pins must move together, or restore fails with NU1605. No source changes are needed.

What 1.5.0 changes for the provider

Two changes apply to the HTTP/ADO.NET path that the provider uses:

  • Fixed/UTC timezone read fix. A DateTime/DateTime64 column whose Fixed/UTC±HH:MM:SS timezone name has a minute or second field above 59 now reads with the correct wall clock. Servers before ClickHouse 26.10 carry the excess into the next field, so Fixed/UTC+05:60:00 is +06:00; 26.10 rejects the name. The driver rejected such a name and read the value as UTC. (clickhouse-cs#612)
  • RowIndex on ClickHouseBulkCopySerializationException. When an insert fails because a value cannot be serialized, the exception gives the zero-based position of the failed row in the driver batch. This applies to SaveChanges and BulkInsertAsync, which both use InsertBinaryAsync. The driver starts a new batch every InsertOptions.BatchSize rows (100,000 by default), and SaveChanges makes one insert call for each table and column set, so the index is not a position in the EF batch or in the input sequence. (clickhouse-cs#608)

The rest of 1.5.0 is the experimental native TCP client (ClickHouseTcpClient). It has no ADO.NET layer, so the provider does not use it.

Docs

v0.3.1 is not released, so the Dependencies entry in CHANGELOG.md and RELEASENOTES.md now records the net change for the release, 1.3.0 to 1.5.0. The existing 1.4.0 behaviour notes (zstd responses, InvalidOperationException on a reader with no current row) stay, and are marked as 1.4.0 changes.

Verification

  • Restore resolves ClickHouse.Driver 1.5.0 in every project (checked in project.assets.json), with no NU warnings.
  • dotnet build --no-incremental: 0 errors, 326 warnings. This is the existing baseline, so 1.5.0 adds no warnings.
  • I did not run the test suites locally. Docker was not available on the machine, and both suites need Testcontainers. CI runs both suites against a real ClickHouse server on this PR.

Effect on open PRs

🤖 Generated with Claude Code

Move the driver pin from 1.4.0 to 1.5.0 in the provider and in both test
projects. The three pins must move together, or restore fails with NU1605.

v0.3.1 is not released, so the Dependencies entry in CHANGELOG.md and
RELEASENOTES.md now records the net change for the release, 1.3.0 to 1.5.0.
The 1.4.0 behaviour notes stay, and are marked as 1.4.0 changes.

Two 1.5.0 changes apply to the provider's HTTP/ADO.NET path:

- A DateTime/DateTime64 column whose Fixed/UTC timezone name has a minute
  or second field above 59 (Fixed/UTC+05:60:00 is +06:00 on the server)
  now reads with the correct wall clock. The driver read it as UTC.
- ClickHouseBulkCopySerializationException has RowIndex, the zero-based
  position of the failed row in the batch.

The rest of 1.5.0 is the experimental native TCP client. It has no ADO.NET
layer, so the provider does not use it.

No source changes were needed. The solution builds with 0 errors and 326
warnings, which is the existing baseline. project.assets.json resolves
ClickHouse.Driver 1.5.0 in every project.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@codecov

codecov Bot commented Oct 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@alex-clickhouse
alex-clickhouse merged commit 6b522c9 into main Oct 14, 2026
3 checks passed
@alex-clickhouse
alex-clickhouse deleted the alex-clickhouse/bump-driver-1.5.0 branch October 14, 2026 15:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant